home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19970929-19971216 / 000337_news@newsmaster….columbia.edu _Fri Dec 5 10:21:26 1997.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA22404
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Fri, 5 Dec 1997 10:21:25 -0500 (EST)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA18523
  7.     for kermit.misc@watsun; Fri, 5 Dec 1997 10:21:25 -0500 (EST)
  8. Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
  9. From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: Why suddenly "Too many macro names"???
  12. Date: 5 Dec 1997 15:21:23 GMT
  13. Organization: Columbia University
  14. Lines: 15
  15. Message-ID: <66965j$s90$1@apakabar.cc.columbia.edu>
  16. References: <19971205080201.DAA29956@ladder02.news.aol.com>
  17. NNTP-Posting-Host: watsun.cc.columbia.edu
  18. Xref: news.columbia.edu comp.protocols.kermit.misc:8132
  19.  
  20. In article <19971205080201.DAA29956@ladder02.news.aol.com>,
  21. TRock <trock@aol.com> wrote:
  22. : I've just upgraded my application from using MS Kermit 3.12 to 3.15.  After
  23. : resolving some minor syntax changes andfiguring out where KERMIT was
  24. : stashing it's 'connect' screens, it runs fine... for awhile, then suddenly I
  25. : get a rash of messages "Too many macro names".... repeated until it hangs.
  26. : 
  27. : Too many where? why? why only after several screen changes?
  28. : 
  29. We'd need to see what you did (i.e. what commands were executed) to lead up to
  30. this event.  However, one likely cause might be that you have defined a macro
  31. that is too long.  I believe the limit is about 1000 characters.  If that's
  32. the case, try breaking the long macro up into short ones.
  33.  
  34. - Frank